Netware Super Library

home *** CD-ROM | disk | FTP | other *** search

/ Netware Super Library / Netware Super Library.iso / file_mgt / gledit / gledit.doc next >

Wrap

Text File | 1995-03-20 | 41.9 KB | 947 lines

GLEDIT Global File Editor USER'S GUIDE Copyright 1990 by Gary C. Crider TABLE OF CONTENTS: What is GLEDIT? .................................. 1.0 The GLEDIT Command Line .......................... 2.0 The GLEDIT Text Mode User Interface .............. 3.0 The Primary Data Entry Screen .................. 3.1 Data Entry ..................................... 3.2 The Options Selection Window ................... 3.3 Context-Sensitive Help ......................... 3.4 Inputing Search/Replace Strings from a File ...... 4.0 Escape Sequences for Special Characters .......... 5.0 Operational Notes and Cautions ................... 6.0 Locating Data .................................... 7.0 Modifying Data ................................... 8.0 Printing or Saving the Output .................... 9.0 Return Codes ..................................... 10.0 Compatibility with Prior Releases ................ 11.0 The GLEDIT.INI Configuration File ................ 12.0 Installation ..................................... Appendix A Disclaimer ....................................... Appendix B Support .......................................... Appendix C Registration ..................................... Appendix D 1.0 What Is GLEDIT? GLEDIT lets you globally search for, and optionally replace, a string of characters in all selected files a directory or directory tree. If you have used any text search utilities, you know the power of being able to search all .BAT files in your BATCH directory when you move some applications to a new disk volume. You are able to tell immediately which batch files need to be modified. GLEDIT takes it a step further in letting you also specify the string that is to replace the search string and does the update of the file for you. It prompts you before changing each line that may require modification. Option- ally, the prompting may be supressed. 2.0 The GLEDIT Command Line If GLEDIT is entered at the command line with no parameters, the GLEDIT text mode user interface will be invoked. It is a full screen, windowed interface to using GLEDIT with context-sensitive help. Please see the next section if you wish to use the interface. GLEDIT can also have all of its parameters input on the command line if the search and/or replace strings are not too long. Format: GLEDIT [path]filespec "searchstring" ["replacestring"] [switches] The "filespec" is the file name of the file that you want to search or edit. If the "filespec" is a wildcard specification, all matching files in "path" will be searched/edited. If "path" is not specified, the current directory is used. If a mapped network directory is used for the path, the full directory path should be specified, rather than just the drive letter. For example, use W:\UTIL\*.* rather than W:*.* if W: is mapped to the UTIL directory. Do not use the actual network drive names in the path such as APPL:\UTIL\*.*. The "searchstring" is the string of characters to look for in each matching file. It should be enclosed in quotes if it contains spaces, commas or characters other than letters or numbers. The "replacestring" is the new string to be inserted in place of the "searchstring". It does not have to be the same length as the "searchstring". The new record length will be adjusted to accommodate the replacement. It should be enclosed in quotes if it contains spaces, <, >, |, or /. If you specify "" as the "replacestring", then nothing is inserted in place of the "searchstring", in effect deleting it from the record. Either string may contain quotes by using the ~q escape sequence described in the next section. See the section, "Escape Sequences for Special Characters" for information on including quotes within the search or replace string. Also see the section, "The GLEDIT Text Mode User Interface" regarding the use of quotes in strings input via the interface. The replace string may not be exactly the same as a switch (see below), unless enclosed in quotes. The switch characters may also be embedded within a replace string. See section 2.1 for instructions on inputing the search and/or replace strings from a file. Switches: /I indicates case-insensitive searching where the search argument and the target record will match if they contain the same letters regardless of upper or lower case. /I has no effect on "replacestring". The "replace- string" is inserted as entered in the command line. /N directs output to the standard output device (normally the display). GLEDIT normally writes to the screen with color highlighting of the matched string. Output directed to the screen cannot be redirected to another device. The standard output can be directed to another device such as a file or printer. If you specify /N and do not redirect the output, it will appear on the screen without color highlighting. /D causes matching lines to be deleted. Prompting occurs unless /Y is specified. /S in most instances, causes information to be sent to the screen contin- uously, with no pauses when the screen gets full, or a new file is processed. Scrolling depends on both /S, /Y and the mode of operation. See the table in "Operational Notes and Cautions" for specifics of how this parameter will impact the display. /Y is used to automatically reply Y to the replace prompts when in edit (replace) mode. Please see "Operational Notes and Cautions" before using this parameter. It is ignored in search mode. Screen scrolling depends on both /S, /Y and the operational mode. See the table in "Operational Notes and Cautions" for specifics of how this parameter will impact the display. /T (test mode) performs normally except that no changes are actually made to any files. You can test the results before proceeding. /T is ignored in search mode. Some messages are slightly modified to indicate that the changes are not actually made. /P tells GLEDIT that this is a search mode run only, and the only thing displayed will be the path and filename of any files which conatin the search string. If /P is specified, the replace string is ignored as are the /T, /Y, and /D switches. /R tells GLEDIT to search the current directory and all subdirectories subordinate to the current directory. 3.0 The GLEDIT Text Mode User Interface If GLEDIT is entered at the command line with no parameters, the GLEDIT text mode user interface will be invoked. It is a full screen, windowed interface to using GLEDIT. Not just a front-end, the user interface is a container that completely envelopes GLEDIT with easy entry of search parameters, option setting and context-sensitive help. In following sections, if there are any differences in operation or results in the user interface and command line mode, a notation will be made relating the differences. 3.1 The Primary Data Entry Screen Typing GLEDIT with no parameters invokes the data entry screen which allows you to enter the file path and filename/wildcard mask, and the search and replace strings up to 512 bytes each. The path field tells GLEDIT what file(s) to search/edit. It may contain any valid DOS drive/path/filename, path/filename or just filename. The filemane may be a wildcard construct, using normal DOS wildcard conventions. If the drive and/or path is omitted, the current drive and/or path is assumed. If the path is a wildcard specification, all matching files in the directory (and subdirectories if the recurse option is selected) will be searched and, optionally, edited. If a mapped network directory is used for the path, the full directory path should be specified, rather than just the drive letter. For example, use W:\UTIL\*.* rather than W:*.* if W: is mapped to the UTIL directory. Do not use the actual network drive names in the path such as APPL:\UTIL\*.*. The path field may not be left blank. Up to 64 characters, upper or lower case may be entered. The search string is the string of characters to look for in each requested file. The search string field may not be left blank. Up to 512 characters, upper or lower case may be entered. The replace string is the new string to be inserted in place of the search string. It does not have to be the same length as the search string. The new record length will be adjusted to accommodate the replacement. If you specify the string "" as the replace string, then nothing is inserted in place of the search string, in effect deleting it from the record. The replace string field may be left blank to indicate that search mode is being invoked. Up to 512 characters, upper or lower case may be entered. The search and replace string fields are actually made up of eight fields each that are combined into one field for GLEDIT. Type the information continuously, continuing words across the end of a line just as if the multiple lines were really one long line. Don't deliberately break between words like a word processor would do. When the field is built for processing by GLEDIT, trailing blank lines are discarded, the remaining lines are concatenated together, and trailing blanks are removed. Lastly, one quote is removed from the front and back of the field if they exist. This is to allow trailing blanks in the search string. 3.2 Data Entry To enter data in a field, move the cursor to the field by using the TAB, ENTER or up and down arrow keys. TAB and ENTER move the cursor down the window to the beginning of each input field. The up and down arrows move up or down to the next line or field. You may now enter your new information in the field. Press ENTER or TAB to move to the next field. F10 accepts all input and processes the screen when pressed in any field. Pressing ESC allows you to cancel any input and exit the data entry window. If, after entering data in a field, the cursor does not proceed to the next field, there is an error in the data entered in the field. Each field is audited to make sure that what you enter is acceptable to the program. If you try to enter a character and nothing appears on the screen and the cursor remains stationary, it is because you are trying to enter a character which is not acceptable in that position of the field. For instance, nothing will happen when you try to type "1" in the OPTIONS fields which only accept "X" or space. Input Field Editing Keys: Left Arrow Cursor left Right Arrow Cursor right Up Arrow Cursor up Down Arrow Cursor down CTRL-Left Arrow Word left CTRL-Right Arrow Word right Tab Field right SHIFT-Tab Field left Enter (Return) Process field CTRL-Enter Process screen Decimal (.) Move to right of decimal Home Beginning of field End End of field data CTRL-Home Beginning of first field CTRL-End End of last field Insert Toggle insert mode on/off Delete Delete character at cursor Backspace Delete character left of cursor CTRL-Backspace Delete word to left of cursor CTRL-R Restore field to original contents CTRL-T Delete word to right of cursor CTRL-U Delete to end of field CTRL-Y Delete to end of last field Esc Abort data entry. F10 Process screen (On data entry window) F10 Select for update (On browse window) 3.3 The Options Selection Window The options window allows you to modify certain parameters of a given search/ replace session. These are mostly the same options that are available on the GLEDIT command line. To select/deselect an option, place an 'X' or space respectively in the box beside the option. You can set your own default options in GLEDIT.INI. The "Ignore case" option lets you determine if caps/lower case should be considered in searching. If you place an 'X' in this box, a case-insensitive search is performed. Replace strings always retain their case as entered. The "Delete matching records" option allows you to delete records which contain matches to the search string. Placing an 'X' in this box puts GLEDIT in delete mode. The "Scroll window without pause" option controls whether the screen scroll will pause when the screen is full or the searched file changes. The actual effect of this parameter, or lack of it, varies depending on whether you are in search, replace or delete mode and the status of the "Prompt before action" option. To see how use of this parameter will effect operation, use the "Test mode option" or refer to the table in the "Operational Notes and Cautions" section. The "Prompt before action option" determines whether or not you will be prompted before a replace or delete takes place. Placing an X in this box forces GLEDIT to query you prior to making each change in the file. If this option is turned off, no such query is made and the replacement/deletion takes place. The "Test mode" option allows you to operate GLEDIT normally except that no changes are actually made to the file. You can see the results beforehand. Place an 'X' in this box to prevent file modifications. The "Recurse subdirectories" option will allow you to search files in all levels of the directory tree including and subordinate to the specified directory. Placing an 'X' in this box tells GLEDIT to search all sub- ordinate directories as well as the current directory. The "Show paths/filenaes only" parameter tells GLEDIT that this is a search mode run only, and the only thing displayed will be the path and filename of any files which conatin the search string. If specified, the replace string is ignored as are the "test mode", "Prompt before action" and "Delete matching records options. 3.4 Context-Sensitive Help One of the primary advantages to using the user interface is that help is just a keypress away. To enter the Help function, place the cursor on the field for which you need help and press F1. Exit help at any time by pressing ESC. Page Down and Page up can be used to view multiple pages of a single help category. Other help categories will be displayed at the end of the help screen which may also contain information concerning the item you have selected. To access these categories, move between them with the arrow keys and press ENTER to select the one you want. The help index contains all help categories, each of which is selectable by using the arrow keys and ENTER. 4.0 Inputing Search/Replace Strings from a File You can avoid the limitation imposed by the DOS command line length by telling GLEDIT to get the search string and/or the replace string from a file, rather than directly from the command line. This even works in the user interface mode, although the benefits are less readily discernable. First, prepare an ASCII text file (not a word processor format file) with any text editor. This file should contain a single line up to 512 characters long that will be the search or replace string. If it contains leading or trailing blanks, enclose the string in quotes. You then reference the file path/name in the command line in place of the search or replace string parameter by preceding the file path/name with @. For example, if you want to replace the string "all good men" with a string in AGM.TXT in the current directory, the command line would look like this: GLEDIT *.TXT "all good men" @AGM.TXT Or if you wanted to search for the string in AGM.TXT and replace it with "all good men", and the AGM.TXT file is in the D drive root directory (not the current directory), the command line would look like this: GLEDIT *.TXT @D:\AGM.TXT "all good men" Suppose you want to specify both the search and replace strings in files. You can create a file with the search string and another with the replace string and specify both file names in the command line. Or you can include two lines in the same file. The first line would be the search string and the second is the replace string. To tell GLEDIT to look for this arrange- ment, you specify the same file name in both places in the command line. For example, if file AGM.TXT looks like this: all good men and the file QBF.TXT looks like this: quick brown fox the following command line: GLEDIT *.TXT @AGM.TXT @QBF.TXT replaces all occurrences of "all good men" with "quick brown fox". An alternative would be to create a file, AGMQBF.TXT that contains both lines: all good men quick brown fox and then use the following command line: GLEDIT *.TXT @AGMQBF.TXT @AGMQBF.TXT to achieve the same results. One last shortcut is to specify the second filename as just @. This tells GLEDIT to use the same file for the replace string just as if you had typed the file name twice. In other words you can perform the same example as above with the following: GLEDIT *.TXT @AGMQBF.TXT @ If you want to actually specify @ or a string that starts with @ as a search or replace string on the command line, use ~@ as explained in the next section. 5.0 Escape Sequences for Special Characters Sometimes ASCII text files contain some special characters that are not normally considered text characters. GLEDIT lets you search and replace using some of these characters by substituting escape sequences in the search/replace strings for these characters. Please read the notes below concerning each escape sequence before using them. The following escape sequences are used within the searchstring and replacestring to represent the presence of special characters that either cannot be entered on the command line, or may cause problems if they are. The character following the tilde (~) must be lower case. ~b = Bell [BEL] (ASCII 7) ~e = Escape (ASCII 27) ~f = Form feed (ASCII 12) ~p = Percent sign [%] (ASCII 37) ~n = Line feed (ASCII 10) ~q = Double quote ["] (ASCII 34) ~r = Carriage return (ASCII 13) ~t = Horizontal tab (ASCII 9) ~~ = Tilde [~] (ASCII 126) ~@ = At [@] (ASCII 64) NOTES- ~b - The BEL character causes a beep on the speaker when displayed, but does not display as any character. In order for you to see where it is located in the line, the prompts will display the BEL character as a heart. It will not show up at all when /N is specified. ~e - The ESC character is used to indicate ANSI.SYS and printer escape (control) sequences. To prevent interference with the display, the prompts will display the ESC character as a happy face. It will not show up at all when /N is specified. ~f - The form feed character causes the printer to eject a page. It shows up on the prompt line as circle over a cross, the female sign. To prevent page ejects when routed to a printer, it is omitted from the prompt lines when /N is used. ~p - Using the ~p sequence in place of the percent sign (%) prevents DOS from trying to interpret %1-%9 and paired percent signs as command string and environment variables when GLEDIT is executed within a batch file. DOS attempts this variable substitution regardless of the presence of quotes in the line. If the variable is not found in the command line or environment, whatever it interprets as a variable vanishes. This is true even if there are spaces between paired percent signs. This is only necessary to be used in command line mode. ~n - The line feed causes the printer or display to advance one line. Inserting a line feed will split a line of text into two lines. When adding a ~n you are actually inserting carriage return/line feed (CR/LF) pairs. These CR/LF pairs are found at the end of each text file record. You cannot search for line feeds, but you can insert them in the replace string. See the note on ~r. ~q - Double quotes within the search/replace strings must be entered using the ~q escape sequence when in command line mode because otherwise DOS will misinterpret the command line. The \q which was used in early releases is no longer supported. If using the user interface, the ~q is not needed and the " can be entered directly in the search or replace string. Be aware, however, that quotes which begin or end the string are removed. This allows leading and trailing blanks to be included in the string. ~r - The carriage return character causes the printer or display cursor to return to the start of the current line. The Borland C++ text mode input routines ignore carriage returns, and read in carriage return/ line feed pairs (CR/LF) as line feed characters. Thus, a search for a carriage return will always fail to find a match. You may, however insert carriage returns by putting them in the replace string. See the note on ~n. ~t - The horizontal tab character displays or prints a number of spaces whenever it is sent to the display or printer. Usually this defaults to 8 spaces, but can be set to other values within many programs. The tab shows up in prompts as a diamond character. ~~ - You may search for or replace the tilde character by using two tildes (~~) to represent one. If a single tilde is encountered that is not followed by one of the above lower case letters, it is treated the same as ~~. ~@ - The @ sign is used to denote input redirection on the command line, therefore, if your search or replace string starts with @, you must use ~@ instead. The @ sign can be used elsewhere in the parameter without the tilde. Some uses for special characters include splitting lines by inserting ~n, replacing tab characters with the desired number of spaces, removing form feeds from printer files, searching for and replacing laser printer escape sequences, etc. If your keyboard does not have a tilde, hold the ALT key down and press 126 on the keypad. Most international and graphic characters can be entered in the same manner, by holding the ALT key and entering the decimal value of the ASCII code on the numeric keypad. PLEASE NOTE- Some of the special characters are removed from the records displayed on the screen due to the unwanted results they might cause when displayed or redirected to a printer. These characters are ~b, ~e and ~f. The characters are present, however, in the records read from or written to the file. 6.0 Operational Notes and Cautions Please note that GLEDIT is intended for use with ASCII text files that use the standard CR/LF record delimiters. If you use it on binary or non- standard files, the resulting file will probably be unusable. If you use GLEDIT on indexed database records and substitute unequal length strings, you are almost sure to corrupt your database. GLEDIT does not back up files before replacing them, so be careful and be sure of what you are doing. The safest approach is to backup the directory, possibly in an archive (.ZIP, .ARC, etc.) file before editing with GLEDIT. GLEDIT has two modes of operation, search and edit. Whenever a replacement string is specified, edit mode is activated. If no replacement string is provided, search mode is invoked unless /D is specified. /D also invokes a special edit mode known as delete mode. In search mode, no file writes whatsoever take place, therefore no data is modified. When edit mode is invoked, a work file is written to the target directory. As each record is read in, it is also written to the work file, modified or not. When GLEDIT reaches end of file on the input file, it checks to see if you had elected to make any modifications. If so, it copies the work file over the input file. The point of relating all of this is that you should not specify a replacement string if you are just looking for occurrences of a string. Edit mode has much higher overhead. Please be extremely cautious when using the /Y parameter. This is for users who like to live on the edge and believe, "It's my data and I'll corrupt it if I want to." A miskeyed command line or not thinking through what is going to be the result can cause file damage on a vast scale. If /Y is specified, the only way to stop it is with ESC or CTRL-BREAK. CTRL- BREAK could cause a file to be damaged, so ESC is recommended. Use the /T switch to test the result before proceeding with /Y. It is a good idea to use /N and redirect the output to a file or printer during execution of /Y or /T. This gives a log of the results. See Printing or Saving the Output. If at any time you wish to abort a search, press the ESC key. The effects of the /S and /Y switches to scrolling are dependent on the mode. Below is a table of valid combinations and what happens when the parameters are specified. Pause at Pause when Prompt for MODE SWITHCES end of file? screen full? replace/delete? Search Y Y N/A Search /S N N N/A Replace/Delete N N Y Replace/Delete /S N N Y Replace/Delete /Y Y Y N Replace/Delete /S /Y N N N Notes: /Y is ignored in search mode. /S is equivalent to marking the "Scroll window without pause" box in the options window. /Y is equivalent to not marking the "Prompt before action" box in the options window. 7.0 Locating Data The primary purpose of GLEDIT is to let you find files that contain certain strings, generally because the strings need to be modified, but not always. If you just want to find what files contain a certain string, just enter the GLEDIT command without a replacement string. GLEDIT will begin going through the target directory finding each file that matches the filespec you provided in the command line. It will search each of the matching files for the search string you provided. When found, the file name will be displayed along with any records in the file containing the search string. 8.0 Modifying Data Edit mode processing involves everything described under Locating Data plus you are prompted to reply Y or N depending on whether or not you want matching records updated as each is displayed. GLEDIT also displays the modified line as it will appear if you reply Y. You can see the result before you accept it. If you specify "" as the replace string, any matches of the search string are deleted from the record. Please note the difference between this and the /D switch. The /D switch or "Delete matching records" option causes the entire line to be deleted, whereas the "" replace string only causes the search string to be removed from the current line. 9.0 Printing or Saving the Output To print the output of a search, or an edit using /Y or /T, specify the /N, and /S if in search mode, parameters and redirect the output to the printer: GLEDIT *.TXT "MOM" /N /S >PRN or log to a file: GLEDIT *.BAT "G:" "H:" /N /T >C:\GLEDIT.LOG You can use >> instead of > if you want the output appended to a log file instead of creating a new log each time. Do not use redirection when using edit mode (without /Y or /T) or without the /S in search mode. The resulting pauses will make it appear that GLEDIT is hung, since you will not see the prompts. If this happens, repeatedly pressing N will allow GLEDIT to progress to completion. This redirection cannot be used when using the user interface. 10.0 Return Codes The following DOS ERRORLEVEL return codes are returned from GLEDIT: 0 - One or more matches found. Replaced or not replaced has no bearing. 1 - No matches found in any files searched. 2 - No files found matching the search file specification. 3 - Invalid path specified in search file specification. 4 - Directory recursion error. Please report to Parity Solutions. Should never happen. 255 - User abort. ESC key pressed. Does not detect BREAK key. 11.0 Compatibility with Prior Releases Versions prior to 2.5 used \q to indicate a quote within a search/replace string. This is no longer supported. The ~q escape sequence is used instead (command line mode only). If you have edits set up in batch files or scripts, check them to make sure that the search and replace strings do not contain any of the allowed escape sequences. If they do, replace the tilde (~) with two tildes (~~). This is necessary when going from a release prior to 2.5 to release 2.5 or later. See the section, Escape Sequences for Special Characters. Very early releases used /D to delete the search object from the record. This is now accomplished by using "" as the replace string. Version 4 now uses the /D switch to indicate that matching records should be deleted altogether. 12.0 The GLEDIT.INI Configuration FIle The GLEDIT.INI file tells GLEDIT what colors to use, what options are the defaults, et cetera. A sample GLEDIT.INI file comes with GLEDIT and is initialized to all of the defaults. The defaults are used when the GLEDIT.INI file cannot be found or when a particular setting is missing from the file. The GLEDIT.INI file can be changed with any text file editor and should be saved in a directory that is specified in DOS's PATH= environment variable. As a last resort, if GLEDIT.INI is not found on the path, it also looks in the same directory from which GLEDIT.EXE was loaded. Thus, if you keep GLEDIT.EXE and GLEDIT.INI in the same directory, GLEDIT should never have trouble locating it. All of the settings and values for the GLEDIT.INI file are documented within the GLEDIT.INI file provided with GLEDIT.EXE. If you wish to add comments to the file, the first non-blank character on the line should be a semi-colon (;). APPENDIX A Installation GLEDIT is distributed in a self-extracting ZIP file called GLEDT.EXE or a ZIP file called GLEDIT.ZIP. It contains the following files: GLEDIT.EXE The executable file for GLEDIT. GLEDIT.INI The configuration file for GLEDIT. GLEDIT.DOC The documentation file. GLEDIT.HST History of changes to GLEDIT. GLEDIT.HLP Context-sensitive help file. GLEDIT.Vnn Description of changes to implement version nn, the current version. PRODUCTS.DOC A text file describing all Parity Solutions products. For best results, unzip the file into a directory on your PATH. If you don't use a directory in your path, you will have to designate the directory containing GLEDIT.EXE when executing the program. Make sure the GLEDIT.INI and GLEDIT.HLP files stay in the same directory as GLEDIT.EXE. If you have a utility directory that is on your PATH, this is an excellent location for GLEDIT. An example installation would be: C: CD \UTIL COPY [path]GLEDT.EXE GLEDT DEL GLEDT.EXE or C: CD \UTIL COPY [path]GLEDIT.ZIP PKUNZIP GLEDIT DEL GLEDIT.ZIP If they are not currently in your path, simply copy all of the files to a directory in your path. Keep the ZIP file anywhere you like, but give plenty of copies, as is, to your friends. If you register GLEDIT, you are not licensed to give your serial number to anybody without first removing the serialization from your copy. If you do not desire to keep all the files together in a directory on your path, please see the "GLEDITFilesPath=" parameter in the GLEDIT.INI file for instructions on how to tell GLEDIT where your files are located. APPENDIX B Disclaimer BECAUSE OF THE DIVERSE NATURE OF COMPUTER EQUIPMENT AND EXPERTISE OF USERS, PARITY SOLUTIONS AND GARY C. CRIDER MAKE NO WARRANTY ON THE GLEDIT PROGRAM WHATSOEVER, EXPRESSED OR IMPLIED. THE USER ASSUMES ALL RISK OF DAMAGE TO DATA OR EQUIPMENT RESULTING DIRECTLY OR INDIRECTLY FROM THE USE OR MISUSE OF THIS PROGRAM PRODUCT. THE USER MUST BE AWARE THAT USING GLEDIT TO MAKE ALTERATIONS TO PROGRAMS OR DATA CAN RENDER THAT PROGRAM OR DATA USELESS. USERS ARE ADVISED TO TEST MODIFICATIONS MADE WITH GLEDIT THOROUGHLY ON FILES FOR WHICH A BACKUP EXITS. ANY LIABILITY OF THE AUTHOR OR PARITY SOLUTIONS IS LIMITED TO REPLACEMENT OR REFUND OF THE REGISTRATION FEE. APPENDIX C Support I have tried to test the program to the fullest, but I am limited as to systems and configurations with which to test. I have been programming for 18 years and the one thing I know for sure is that bug free programs are very few and far between. I can only promise to support the program to the best of my ability and provide fixes as expeditiously as possible. GLEDIT has been used at my home and work site extensively for several years and has proven to be a reliable tool. Anyone can report problems and suggest changes. Registered users get top priority in resolving their problems. There are three ways you can report problems. The preferred method is to contact me through CIS mail (not forum messages). My CIS ID is 71760,3413. You can also write me at: Gary C. Crider Parity Solutions 1903 Pavia Court Arlington, TX 76006 The last method is to phone (817) 261-9552. Since I am the sole technical support and the line is also used for my network consulting business, it is often hard to get through to me. Please call and leave a message between 7:30 am and 6:30 pm Central time. No matter which method you use, please give a brief description of your problem, your registration serial number if you are registered, and your phone number. If I need more information, I will contact you as soon as I can. When I have a solution, I will contact you however you prefer. I work full time, have a consulting business to run in my spare time and write programs instead of sleeping. So please be a little patient with me. Program updates are available on CompuServe or can be requested from us for a $5 shipping and handling charge. Add $1 for international shipping outside the North American continent. A distribution disk of all Parity Solutions products will be sent to you. Specify disk size and format. You may use the order form at the end of this document. APPENDIX D Registration I begin with an apology. I hate programs that in any way inhibit func- tionality or performance for the shareware version. But when it came down to feeding the family and paying the bills, I had a change of heart and inserted a pesky notice that pops up at the beginning and gets on your nerves. I chose this approach above that of limited functionality. The program's full capabilities are available for you to evaluate before you invest your hard- earned money. You may use GLEDIT unlicensed for 30 days, after which time you are required to be registered. Registered users will receive a unique serial number and instructions on how to serialize the program. Serialization can be re-applied to updated versions and in no way hinders your use of the program. You can compress or decompress the program with no effect (LZEXE or PKLITE). As a registered user, you will be able to update without re-registration or additional fees. You will also be kept on my PRIVATE mailing list to receive additional information on other Parity Solutions products. To register your copy, please use the order form below and send $21 ($85 per file server on LANs) check or money order (sorry, no credit cards yet) to: Gary C. Crider Parity Solutions 1903 Pavia Court Arlington, TX 76006 Please use the order form at the end of this document for your convenience and ours. Purchase orders are acceptable from U.S. and Canadian companies and institutions. International orders outside the U.S., Canada and Mexico add $1 to the total order for postage. Or, you can register online quickly and simply on CompuServe. Simply GO SWREG and register ID #754. Your registration will be added to your CompuServe bill. International exchange was never easier and you save the $1 international postage charge. If you send your CIS ID or register via SWREG, your registration will be sent to you via CIS mail, along with instructions on how to serialize your copy of GLEDIT. This usually involves one day or less turnaround. Program diskettes are not normally shipped. Normal distribution is via CompuServe. If you need a diskette, please see the instructions under Support above, or use the order form below. You will receive a serial number and instructions for serializing your copy of the program. Each license gives you or your company a single-use permit for GLEDIT. It is not restricted to a single machine as long as no two users can be simul- taneously using the program. As Borland says, "treat it like a book." As an example, if you register GLEDIT for your home computer, but during the day you use a portable or a computer at work, you may keep GLEDIT on both machines as long as no one is at home using it on your home computer. LAN licenses grant rights to all users of a file server. If inter- networking, a license must exist for each file server that contains a copy of GLEDIT.EXE. If two or more file servers exist on a single LAN strictly for mirroring data and fault-tolerance, these will be counted as a single file server for licensing purposes. If in doubt, contact me. We can work out an agreement. Site and enterprise licensing is also available on a negotiated price basis. I guarantee it will be an economical alternative to buying licenses for each user. If you are a registered user of GEDIT from Parity Solutions, you may use your GEDIT serial number to serialize GLEDIT. You may freely distribute the original GLEDIT.ZIP file in any way you see fit other than selling it. Users' groups and shareware distribution services may charge a reasonable fee for the medium and duplication costs, not to exceed six dollars. Bulletin boards may not charge additional fees for downloading this specific program, other than normal connect-time and/or membership charges. You are NOT licensed to give anyone your serial number unless you first remove all serialization from your computer. You may then no longer use that serial number. Only Parity Solutions has the authority to issue serial numbers. Modification of GLEDIT.EXE in any manner is prohibited and unlawful. Licensees of Parity Solutions' GEDIT program may serialize GLEDIT by renaming GEDIT.SER to GLEDIT.SER. ============================================================================== ORDER FORM FOR GLEDIT Send checks or money orders payable to: Parity Solutions 1903 Pavia Court Arlington, TX 76006 BILLING ADDRESS: SHIP TO (If different): NAME: _____________________________ NAME: ___________________________ COMPANY: _____________________________ COMPANY: _____________________________ STREET: _____________________________ STREET: _____________________________ _____________________________ _____________________________ CITY/ST: _____________________________ CITY/ST: _____________________________ ZIP/POSTAL CODE: _____________________ ZIP/POSTAL CODE: _____________________ COUNTRY: _____________________________ COUNTRY: _____________________________ PHONE: _____________________________ PHONE: _____________________________ CompuServe/Internet ID: ___________________________________________(optional) NOTE: Parity Solutions sends a serial number for each registration and instructions for serializing your program. A diskette containing the latest releases of all Parity Solutions shareware products is available for $5.00 U.S. The current release of GLEDIT is avail- able for downloading on CompuServe in the PCUTIL forum. QTY DESCRIPTION PRICE EA. TOTAL PRICE ___ GLEDIT license and registration $21.00 ___________ ___ GLEDIT Network license and registration 85.00 ___________ ___ Parity Solutions shareware diskette 5.00 ___________ International postage outside U.S., 1.00 ___________ Canada and Mexico. Total Enclosed: ___________ Diskette size (if ordered): __ 5.25" 1.2M __ 3.5" 1.44M Thank you for doing business with Parity Solutions. (817) 261-9552 Parity Solutions is a partnership of Gary C. Crider and Russell L. McCloud. Federal tax identification number 75-2468376. ==============================================================================